Skip to content

docs: document automation repository boundaries - #369

Open
neubig wants to merge 2 commits into
mainfrom
docs/repository-boundaries
Open

docs: document automation repository boundaries#369
neubig wants to merge 2 commits into
mainfrom
docs/repository-boundaries

Conversation

@neubig

@neubig neubig commented Aug 23, 2026

Copy link
Copy Markdown
Member

HUMAN:

I reviewed the automation service architecture and documented its ownership boundaries and cross-repository workflow.

AGENT:

This pull request was created by an AI agent (OpenHands) on behalf of the user.

Why

Contributors need to know which behavior belongs in the Automation Service versus the Agent Server/SDK, TypeScript client, or Agent Canvas. This prevents duplicated logic and PRs being opened in the wrong repository.

Summary

  • Document automation ownership in AGENTS.md and README.md.
  • Clarify that automation manages when work runs while the SDK/Agent Server executes conversations.
  • Add guidance to move changes to the repository that owns them.

Issue Number

Fixes #368

How to Test

Review the two changed Markdown files for accurate ownership descriptions and repository links.

Video/Screenshots

Not applicable: documentation-only change.

Type

  • Bug fix
  • Feature
  • Refactor
  • Breaking change
  • Docs / chore

Clarify ownership across automation, Agent Server, client, and Canvas repositories.

Fixes #368

Co-authored-by: openhands <openhands@all-hands.dev>
@github-actions github-actions Bot added the type: docs Documentation only changes label Aug 23, 2026
@github-actions

github-actions Bot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Coverage

Keep the cross-repository ownership model consistent with OpenHands extensions.

Co-authored-by: openhands <openhands@all-hands.dev>
@all-hands-bot

Copy link
Copy Markdown
Contributor

🤖 OpenHands is reviewing this PR.

Head commit: 9ff0c671cc84674b5e8f8d1a98eedceaa6382b93
View the conversation: https://oss-agent-canvas.ngrok.dev/conversations/2f133543-eb87-4a90-a519-0db2462ac4b3

This comment was posted by an AI agent (OpenHands).

@all-hands-bot all-hands-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This review was created by an AI agent (OpenHands) on behalf of the repository maintainers.

Verdict: No material findings — approve to merge.

Risk assessment: None. This is a documentation-only change (+19/-0 across AGENTS.md and README.md) with no code, config, migration, or behavioral impact.

Accuracy check:

  • All four cross-repository links resolve to existing repos (software-agent-sdk, typescript-client, OpenHands, extensions), and their stated responsibilities match their actual repo descriptions.
  • The ownership boundary description is correct and consistent with the repository's architecture: this service owns the "when" (scheduling, dispatch, sandbox lifecycle), while the Agent Server/SDK owns the "what" (agent behavior, conversations, workspaces, events, API endpoints).
  • The AGENTS.md guidance to close/move PRs opened in the wrong repository aligns with the cross-repo coordination policy already documented in this file.

Issue #368 acceptance criteria are all satisfied: responsibilities documented for all four repos, the when-vs-what distinction is clear, the SDK/Agent Server ownership of agent behavior/tools/conversations is stated, and the wrong-repo PR guidance plus contribution/code-review requirement are present in AGENTS.md.

Minor note (not blocking): the README.md section omits OpenHands/extensions while AGENTS.md covers it. Since AGENTS.md is the contributor-facing source of truth and fully enumerates all four repos, this is acceptable.

@enyst enyst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Funnily enough, the reviewer agent didn’t approve this one, though this is fine. 😅
Slight redundancy on the first paragraph, since the little previous section says the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: docs Documentation only changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Document repository boundaries for Automation Service

4 participants